Method and apparatus for mobile quality management inspections

ABSTRACT

A mobile Quality Management/Control system for performing mobile product inspections is provided. A mobile device, such as a tablet, is configured to communicate with one or more databases and allow for real time entry (and subsequent access) of the details of product inspections for quality control and management purposes. The details of such inspections are maintained and available for all subsequent inspections. The mobile device is further configured to provide inspectors with inspection procedures and/or tutorials associated with the inspections being performed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser.No. 61/803,501 filed Mar. 20, 2013, which is incorporated by referenceherein in its entirety.

BACKGROUND Technical Field

The present principles relate to quality control in productmanufacturing and production. More particularly, it relates a method andapparatus for quality control/management inspections on site.

Related Art

To date, the quality management inspection process is largely paperbased. Inspectors perform on site source inspections and socialcompliance audits utilizing spreadsheet documentation, and there is novisibility of results available in known and existing Quality Managementinspection systems.

SUMMARY

The quality management inspection system of the present principlesprovides a standardized inspection process that is visible throughoutthe entire supply chain. This present quality management inspectionsystem and method is a mobile solution that completely replaces thecurrent paper based system of results recording.

According to one implementation, the mobile Quality ManagementInspection System includes a mobile device in communication with atleast one network server and a database in communication with thenetwork server. The mobile device has a display screen and input meansfor inputting data, the data including photographs. The database isconfigured to receive and store all data input to the mobile deviceduring an inspection. The mobile device is configured to enable aninspector to perform source inspection; receiving inspection; productqualification inspection; social compliance, CTPAT and factoryvaluations; non-conformance processing and document management andupload this information to the database in substantially real time.

According to another implementation, a method for mobile QualityManagement Inspections includes the steps of creating an inspection lotin response to a vendor's completion of an order and recordinginspection results using a mobile device in communication with at leastone network server. The mobile device has a display screen and inputmeans for inputting data, the data including photographs. Once resultsare recorded, a usage decision process is performed on acceptedinspection lots and a non-conformance process is performed on unacceptedinspections lots.

These and other aspects, features and advantages of the presentprinciples will become apparent from the following detailed descriptionof exemplary embodiments, which is to be read in connection with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present principles may be better understood in accordance with thefollowing exemplary figures, in which:

FIG. 1 is a high level flow diagram of the quality management (QM)inspection process according to an implementation of the presentprinciples;

FIG. 2 is a flow diagram of the inspection lot processing according toan implementation of the present principles;

FIG. 3 is a flow diagram of the non-conformance processing according toan implementation of the present principles;

FIG. 4 is a flow diagram of the usage decision follow up process,according to an implementation of the present principles;

FIG. 5 is a flow diagram of the non-conformance processing, according toan implementation of the present principles;

FIG. 6 is a block diagram of the hardware architecture of the qualitymanagement system, according to an implementation of the presentprinciples;

FIGS. 7-21 are examples of the quality management application displayscreens and layouts of the same as presented to the inspector during theQM procedure, according to an implementation of the present principles;

FIG. 22 is an example of a recording layer of a results recordingdisplay as depicted in FIGS. 13A-13J according to an implementation ofthe present principles.

DETAILED DESCRIPTION

The present principles are directed to Quality Control and QualityManagement inspections during, and more particularly a completelyintegrated method and system for enabling mobile, on site Qualitycontrol and Quality Management inspections.

The present description illustrates the present principles. It will thusbe appreciated that those skilled in the art will be able to devisevarious arrangements that, although not explicitly described or shownherein, embody the present principles and are included within its spiritand scope.

All examples and conditional language recited herein are intended forpedagogical purposes to aid the reader in understanding the presentprinciples and the concepts contributed by the inventor(s) to furtheringthe art, and are to be construed as being without limitation to suchspecifically recited examples and conditions.

Moreover, all statements herein reciting principles, aspects, andembodiments of the present principles, as well as specific examplesthereof, are intended to encompass both structural and functionalequivalents thereof. Additionally, it is intended that such equivalentsinclude both currently known equivalents as well as equivalentsdeveloped in the future, i.e., any elements developed that perform thesame function, regardless of structure.

Thus, for example, it will be appreciated by those skilled in the artthat the block diagrams presented herein represent conceptual views ofillustrative circuitry embodying the present principles. Similarly, itwill be appreciated that any flow charts, flow diagrams, statetransition diagrams, pseudocode, and the like represent variousprocesses which may be substantially represented in computer readablemedia and so executed by a computer or processor, whether or not suchcomputer or processor is explicitly shown.

The functions of the various elements shown in the figures may beprovided through the use of dedicated hardware as well as hardwarecapable of executing software in association with appropriate software.When provided by a processor, the functions may be provided by a singlededicated processor, by a single shared processor, or by a plurality ofindividual processors, some of which may be shared. Moreover, explicituse of the term “processor” or “controller” should not be construed torefer exclusively to hardware capable of executing software, and mayimplicitly include, without limitation, digital signal processor (“DSP”)hardware, read-only memory (“ROM”) for storing software, random accessmemory (“RAM”), and non-volatile storage.

Other hardware, conventional and/or custom, may also be included.Similarly, any switches shown in the figures are conceptual only. Theirfunction may be carried out through the operation of program logic,through dedicated logic, through the interaction of program control anddedicated logic, or even manually, the particular technique beingselectable by the implementer as more specifically understood from thecontext.

In the claims hereof, any element expressed as a means for performing aspecified function is intended to encompass any way of performing thatfunction including, for example, a) a combination of circuit elementsthat performs that function or b) software in any form, including,therefore, firmware, microcode or the like, combined with appropriatecircuitry for executing that software to perform the function. Thepresent principles as defined by such claims reside in the fact that thefunctionalities provided by the various recited means are combined andbrought together in the manner which the claims call for. It is thusregarded that any means that can provide those functionalities areequivalent to those shown herein.

Reference in the specification to “one embodiment” or “an embodiment” ofthe present principles, as well as other variations thereof, means thata particular feature, structure, characteristic, and so forth describedin connection with the embodiment is included in at least one embodimentof the present principles. Thus, the appearances of the phrase “in oneembodiment” or “in an embodiment”, as well any other variations,appearing in various places throughout the specification are notnecessarily all referring to the same embodiment.

The present principles provides a mobile solution which enables a mobilesystem for ensuring compliance with customer and regulatory requirementsat the following inspection stages: source inspection; receivinginspection; product qualification inspection; social compliance, CTPATand factory valuations; non-conformance processing and documentmanagement.

Within the context of the present disclosure, source inspection is theinspection of products at the factory location prior to being shipped tothe customer ordering the same. Receiving inspection is the inspectionof received products prior to being considered acceptable for use byproduction. Product qualification inspection is the inspection of aproduce prior to full production for the purpose of qualifying theproduction process. Social compliance, CTPAT and factory valuation areinspections that are required to be performed as part of a vendor auditprocess. Non-conformance processing is the ability to record and analyzenon-conformance data. Document management is the electronic managementof all documentation related to production and/or purchasing ofmaterials/parts.

Those of skill in the art will recognize that the exemplary embodimentsof the present principles are described in the context of a system whatworks with SAP® software systems for Quality management (e.g., SybaseMobility Suite)—SAP is registered trademark of SAP Aktiengesellschaft inGermany. However, such integration with known quality managementsoftware systems and databases is only one implementation and otherindependent systems and databases can be also implemented with thepresent principles without departing from the intended scope thereof.

As referred to herein, when applicant states that data is “sent to SAP”,the intended meaning is that the inspection data is sent to the SAPSybase mobility database maintained by the respective customerperforming the inspection, in accordance with SAP's licensing and userequirements.

There are several process steps in the mobile quality management (QM)inspections systems of the present principles. FIG. 1 shows the summaryof the process 10 for mobile management inspections according to animplementation of the present principles. Various details of theprocesses will be described in further detail below. Initially, a vendorconfirms completion 12 of an order. A manager creates an inspection lot14 for that order. The inspector records inspections results 16, and anautomated usage decision 18 is performed on the accepted inspectionlots. A coordinator is automatically assigned 20 to created qualitynotifications when the inspection lot has not been accepted by theinspector. The Quality Coordinator lists the assigned qualitynotifications 22 and maintains the same while also assigning tasks tousers responsible (24). The users responsible perform and close thetasks when done 26. The Quality coordinator then completes the qualitynotification 28, and executes the usage decision by “Accepting” the same30. If there are any follow up actions to be executed, they are at thispoint in the process (32)

Referring to FIG. 2, there is shown a process overview of the method 100for quality management inspections according to an implementation of thepresent principles. Master data 120 and a purchase order data 140 (e.g.,vendor confirms completion of order) are used to create the inspectionlot which is part of the inspection lot processing 160. Here, theinspection lot has been created by the Manager (step 14, FIG. 1). Aspart of the inspection lot processing, the inspector inspects andrecords the results of their inspection. If there are any defects (180)noted in the inspector's results, a non-conformance process 220 isexecuted. If there are no defects, the automated usage decision process200 is executed.

By way of example, the master data 120 can consist of many differentpieces of data. Table 1 shows an example of such master data, theassociated organization object or master data with correspondingdescriptions.

TABLE I MASTER DATA STRUCTURES Associated Relevant Org. Object or IDMaster Data Master Data Explanation (if necessary) 1 Material PlantMaster Sales Organization Distribution Channel Profit Center 2 QualityMaterial If a source inspection or a vendor Information Plant release isrequired for a material, you Record Vendor must create a qualityinformation record (QIR). The quality info record determines how thematerial can be processed further. 3 Work Plant Center Cost Center 4Catalogs Client Catalogs are used to manage, uniformly define, andstandardize information. They can help you to record and subsequentlyevaluate qualitative data, and to describe problems. 5 Selected Plant Aselected set contains a combination Sets of different codes at plantlevel, for example, coded descriptions of characteristic attributes(such as color, shape, surface characteristics), defect codes or usagedecisions from different code groups. 6 Sample A sampling scheme appliesto the Scheme sample size based on a specific inspection lot quantityand defines the criteria for determining whether and how a sample isaccepted or rejected. 7 Dynamic The basic data record contains theModification definition of the inspection stages, the Rule dynamicmodification time (at lot creation or after the usage decision has beenmade), and the conditions for the inspection stage change. Inspectionstage changes occur on the basis of the inspection results that arerecorded for inspection lots and inspection characteristics (that is, onthe basis of their acceptance or rejection 8 Sample A sampling proceduredefines the Procedure rules that specify how the system calculates thesample size and it contains information about the valuation of aninspection characteristic during results recording (attributive,variable, manual, etc.). 9 Inspection Plant Plan Material Vendor

FIG. 3 shows an example of the process for the inspection lot processing160, according to the present principles. Initially, a new transactionto create source inspection lots is generated 33. Next thecharacteristic results for the new transaction are recorded 34. Oncerecorded, the characteristics window is closed 35. A determination isthen made (36) whether there is defect found in the product beinginspected within the inspection lot (i.e., based on the recordedcharacteristics). If a defect is found, it is recorded 38. If no defectis found, the inspection lot is saved 40. Once saved, a calculation ofthe number of defects recorded (step 38) is compared to the AQL valueand an email is sent 44 to the vendor with the comparison data. Theinspector then decides 46 whether to accept the inspection lot. If notaccepted, a Quality Notification is created and a coordinator isassigned 50. If the inspection lot is accepted, the inspector completesan “Accept” Usage decision 48.

FIG. 4 shows a flow diagram of an example of the Usage Decision process200. Here, a few determinations are made. One, whether a Gold SealSample Acceptance has been achieved 60. Those of skill in the art willappreciate that the “Gold Seal Sample” is what the products beinginspected should be aiming for in quality and all other aspects of theinspection. If yes, the Quality information record is updated 62. Ifnot, a determination is made 64 whether the source inspection isrejected with re-inspection. If yes (i.e., rejected again), the inbounddelivery is blocked and a re-inspection of the lot is scheduled(created) 66. If the source inspection is not rejected withre-inspection, the source inspection lot is identified as a failure 68,and a new source inspection lot is allowed for creation 70.

FIG. 5 shows a flow diagram of example of the non-conformance process220 according to an implementation of the present principles. A list ofQuality Notifications is provided 80. Once the list is provided, aselection of a particular Quality Notification is made 82. Once soselected, Tasks are added as required 84, a user is assigned 86 to eachtask, and an email is sent 88 to the assigned users. Once the task iscomplete 90, the usage decision is recorded 92 (which closes theinspection lot). A determination is then made 94 whether to close theQuality Notification. If yes, the Quality Notification is closed in thebackground of the display 96. If not, the closure of the QualityNotification is not allowed 98, and it must then be manually closed 100.

The above processes are performed using a tablet or other mobilecomputing device that collects enables the user to view the datacollected from all the various logging reports, and/or input their ownQM or QC data based on their respective inspections. The followingdetails the creation of the mobile inspection application that isdeployed to the employee users. As will be understood by those of skillin the art of Quality Control and Quality Management, there are manyusers in the chain that are logging reports on a daily basis from avariety of different facilities (sources). These users previously wouldrecord results on paper and the result would be little visibility to thereporting results, accuracy, outstanding work lists, etc.

In accordance with a preferred implementation of the present principles,the mobile inspection application disclosed herein will deliver properinspection procedures and information (substantially in real time), willallow for results recording (including pictures and locations) and allowusers to easily track inspection activities whether connected to a datanetwork or working in a remote manufacturing facility.

FIG. 6 shows a general block diagram of the mobile inspection system 300according to an implementation of the present principles. An inspectorwith a mobile device 304 is in communication with a network of servers302 which are in turn in communication with the quality coordinators 306and the responsible used 308. The quality coordinators and responsibleusers consistently update their logs/reports to the network services 302via their mobile or stationary computing devices at their respectivelocations. The Inspector, using their mobile device 304, will then havesubstantially real time updated reports from the various sources in thequality control chain, and will be able to make their own inspectionreports which would also be updated and loaded into the network servers302 for access by supervisors, etc.

Those of skill in the art will appreciate that the term “network server”refers to one or more hardware computing/computer devices havingappropriate processing, storage and memory capabilities. The details oftypes of processors, storage and memory are not provided herein, asthose of skill in the art do not require the same. Furthermore, the term“network server” as used herein may refer to “cloud” based servers,“resident” servers maintained by the customer and/or one or more oftheir vendors though contract, or any other computing platform operatingas.

The basis of the Quality Management control application of the presentprinciples is the animated screen flows that provide exactly theinformation the user is looking for without over-cluttering the screenwith information. The following FIGS. 7-21 provide an overview of thedesign, screen sequencing, screen positioning and transitions inaccordance with one implementation of the present principles.

Referring to FIG. 7A, throughout the application, there can be four (4)distinct regions used to present all data. As shown in FIG. 7A and forpurposes of this description, the regions are labeled A, B, C, and D andcan be layout as shown. FIG. 7B shows the main menu or applicationbackground as displayed on a mobile device 304. The background is clearof all extraneous data and essentially acts as the backdrop of the“stack of paper” application design. This application background cancover the entire screen with a series of menu options designated inregion A you will see the main menu. The main menu contains severalstarting points for further information to be brought in from the righthand side of the screen in the other regions B, C and D. These startingpoints include, for example, User 10 (layer 2), Worklist 20 (layer 3),Previous 30 (layer 8), Procedures 40 and Videos 50. The details of eachof these starting points will be described in further detail below.

The application background of FIG. 7B is also referred to as “layer 1”of the application. This layer 1 is preferably always the basis for theapplication. It will not transition off the screen, and other layerswill move over top of it while always remaining in the background andshowing as other layers transition on and off the same.

FIG. 8 shows an example of the User 10 (or layer 2) display according toan implementation of the present principles. A user clicks on “user”from the main menu to access this layer. The user profiled containsrelevant data to transmit to SAP for user login. Additionally, thissection contains application information, system connectivity(connection status), application version, etc. This will also containthe sync functionality (sync button) for pulling data to the applicationfrom the SAP Sybase application.

FIG. 9A shows an example of the Worklist 20 (or layer 3) according to animplementation. The work list is where the user will view alloutstanding inspections. This list will be dynamic and will be sortedfirst by start date, then by factory. The dynamic list will bescrollable and will show all items in an inspectors queue for the next30 days. Both of these pieces of information will be pulled from the SAPSybase application per the data mapping functionality described later.

FIG. 9B shows a schematic example of the worklist screen homepageaccording to an implementation. Here, the dynamic worklist (i.e., theinspections) 200 are each provided in a list. Each line is a differentinspection lot or task. Examples of the current types of inspectionsare: Warehouse audit, Gold Seal Inspection, C-TPAT Inspection, SocialCompliance Audit, Factory Evaluation, Source Inspection, andRe-Inspection. Tasks can range from such follow up actions as call/emaila factory, to go and visit and document findings. In accordance with onepreferred implementation of the present Quality Management system, ascan feature 202 is provided. Utilizing the built in camera of themobile device, the user is able to narrow down the selection ofinspection lots on the worklist homepage by scanning the master barcodeof the carton. Subsequently, with in the individual inspections, theuser is able to use the same scan feature to scan the master, inner andpackaging barcodes, which the QM application of the present principleswill validate against information in the source system, which can besymbolized using a Red “X” or a Green “Check”. As shown in FIG. 9A, thisscan feature is accessed using the “lookup” button on the screen. Inother embodiments, the button can be labeled “Scan” as shown in FIG. 9B.

FIG. 10A shows an example of the View Inspection screen (or layer 4).This layer will contain all of the header level information for the userto review. It will contain factory information, purchase order andmaterial information, gold sample information, inspection status,inspection end date and tools required to execute the inspection.Finally, at the bottom of the displayed layer, a “Start” button isprovided which will bring the user to the list of inspection groups inlayer 5. Additional functions will include, for example, the ability tochange inspection quantity and view gold sample found in region D.

FIGS. 10B-10E show examples of displayed inspection lot header screensaccording to one implementation of the present principles. FIG. 10Bshows an example of the social compliance screen for a specific auditinspection for a vendor as it relates to a specific lot #. FIG. 10Cshows an example of the source inspection display screen which providesinformation as to the vendor, the factory and it's address, adescription of the item, tools required for the inspection (202—See FIG.10D), the lot size and samples quantity 204 (e.g., the sample quantity,the Lot MP quantity and the Sample MP quantity). FIG. 10E shows anotherfeature which may be referred to as a location feature 206 whichutilizes the mobile device's mapping function to show the geographicallocation of the location of the lot inspection.

FIGS. 10F-10H shows examples of the “previous inspections screen”display. Here, the user hits the “previously inspections” button 208(FIG. 10G) and they are brought to the previous inspections screen wherea list of the previous inspections are listed (FIG. 10G), and any onecan be selected and viewed. FIG. 10H shows an example where the user maypress an “email” button 210 and generate a pre-populated email with thecurrent lot information and previously inspection information. Thus, itwill be apparent to those of skill in the art that the ability togenerate and send an email in real time during an inspection, that alsohas the ability to include previous inspection data, is an invaluabletool in the Quality Management/Control field.

FIGS. 10I-10K show examples of the Inspections summary screen display.Here, the user hits the “summary” button 212 (FIG. 10I). This bringsthem to the summary screen (FIG. 10J), where a summary of the inspectionbeing performed is provided. Here the user will have the opportunity tomake changes or edits as they see necessary. As with the previousinspections display, the user continues to have the ability to press an“email” button 210 and prep-populate an email with the current lot andsummary inspection information (FIG. 10K).

FIGS. 11A and 11B show the Inspection groups layer display according toan implementation. This layer serves as a grouping for inspectioncharacteristics found in the inspection criteria layer 6 to be describedbelow with respect to FIG. 12. When pulling data out the Sybase SAPdatabase, there will be a group designation and the inspection grouplist will thus need to be populated. The inspection groups includethings like master carton, carton, packaging, packaging materials, etc.As shown in FIG. 11B there is shown an operations overview which is theresult of the selection of a lot from the worklist screen. Here, on theright side next to each of the inspection group items for the selectedlot, two columns 214 are provided “required” and “open”. This area ofthe display informs the user as to how many characteristics (orquestions) remain open in the reference operation sets. This is a veryhelpful feature in providing the user with a real time indication ofwhat is outstanding in order to complete the respective inspection.

An exemplary table is shown below for the inspection groups of layer 5.

TABLE II Operation # Char Status # char open Lot 6 Complete 4 Carton 5Complete 3 Master 7 Pending 2 Inner 4 Complete 0 Packaging 4 OpenProduct 10  Open TRANSFER

Here, the number of completed characteristics are summarized byoperation. This way the user is provided with a simple way to see ifthere are any characteristics open. According to one implementation, the“Transfer” button is not enabled until all characteristics are complete.

FIG. 12 shows an example of the Inspection Criteria screen display,according to an implementation. The Inspection characteristics arelisted in this layer, and each characteristic will drill in to a resultsrecording layer with more detail and specific fields to be populated.This area is accessed by clicking on the desired inspection group in the“inspections group” screen (layer 5) shown and discussed with referenceto FIG. 11. This inspection criteria part of the application is aware ofconditional inspection characteristics and modifies the displayaccordingly. For example, a characteristic may only be visible if theprevious characteristic is rejected or accepted. Each inspectioncharacteristic item will drill in to the inspection characteristicdetail for that group which is found in the results recording layerdiscussed below. The following table is an example of list ofcharacteristics from a “Lot” operation where the status of eachcharacteristic is provided, and the ability to add any number of defectsexists.

TABLE III Characteristic Status # defects Char 1 Complete 4 Char 2Complete 3 Char 3 Pending Char 4 Complete 0 Char 5 Open Char 6 Open Char7 Open

FIGS. 13A-13J show examples of the results recording display or layer 7according to an implementation of the present principles. This layerdisplays specific criteria, inspection methods and results fields to bepopulated. In addition, users will be able to log defects through thislayer. This layer is accessed by clicking on a desired inspectioncriteria from the inspection criteria layer 6.

Examples of the type of information that can be recorded include,Inspection Operation, Char#, Characteristic Short Text, CharacteristicLong Text, Tools required, Methods—links for (PDF, JPG, MOV),Specification (Pass-Fail/Major from lot), Sample Size (# inspector is toinspect from lot), Inspection Qty (Inspector enters # they inspected),Result recording (pull QAQEE—SUMPLUS), Result recording Long text(inspector to enter—will auto populate the short text to the # of charavail in short text when loading back to SAP, Assign originresult=06—From Mobile data recording, and SUBMIT or SAVE (If there is afailure—record defects required, if not, proceed to nextcharacteristic). FIG. 22 depicts an example of some entries one mightsee on the results recording layer 7.

As noted, the number of units to test is listed, along with the resultcode, the tools required and the method. FIG. 13B shows three screens,where from the operations overview screen on the left, a user selects aReference Operation Set, which then opens a list of characteristics forthe user to record the results. Thus, when the user selects “results” onthe characteristic inquiry “do all samples look the same and match theapproved sample?” the “qualitative results recording” window would openand allow the user to input the details of the results.

FIGS. 13C and 13D show other examples of the results recording screenlayer 7. In accordance with one implementation, reference material forthe user pertaining to a particular characteristic can be made availableas an attachment. For example this may be a jpeg, pdf, video or anyother type of attachment. More than one attachment is also viable. Eachentry criteria includes a photo button 222 which allows the user to takepictures at the characteristic level. Each entry criteria will alsoinclude a note button 224 which allows the user to take notes at thecharacteristic level.

According to one preferred implementation, the application will notallow for characteristics to be locked once they are opened. FIGS.13E-13G show examples of opening and locking characteristics inaccordance with this implementation. Step 1, the user opens Referenceoperation set “Records Review” (FIG. 13E). Upon opening, the two (2)characteristics are locked. At step 2, the user records “no” oncharacteristic #0010, thus opening characteristic #0020, while #0030remains locked (FIG. 13F). If the user changes the answer to “yes” forcharacteristic #0010, this opens characteristic #0030 and locks #0020.This prevents the user from making errors or inadvertently recording aresult for the wrong characteristic, but it also enables some dynamicchanging of the recording of results without having to start over. Thoseof skill in the art will appreciate that if the user was recordingdirectly in the source system, the user would have to cancel the lot andstart from the beginning.

FIGS. 13H-13J show an example of the entry of quantitativecharacteristics using the results recoding layer 7. In step one, theuser hits the “results” button (FIG. 13H). This action opens aquantitative results recording screen where the individual results areentered (FIG. 13I). Once completed, the user hits “record”, and theapplication records the results and returns back to the source system ofindividual results (FIG. 13J).

As part of the inspection process users will need to log defects. Thiswill be handled in defect recordings section (layer 8) of theapplication and will include defect type, description, defect location,etc. In addition, users will have the ability to save multiple picturesof the defect. This section is accessed by clicking on the desiredinspection criterion from layer 6. Generally speaking, when a userrecords a negative answer for a characteristic, the defect recordingsscreen is automatically brought up where they can record the defects.

FIG. 14A shows an example of the defect recordings screen and the datato be included therein. All non-conformance issues will be logged here.The results will go back to the SAP Sybase database when the inspectionis complete. There may be a “defect code” that needs to be populated.The # of defects, the location and details of the same are all to belogged/recorded in this section. One or more pictures may be taken ofthe defect using the picture button. Once completed, the user hits“submit” to record the defect (i.e., send to the SAP Sybase database).In addition to pictures, it is contemplated to enable the taking ofvideo of defects as well, e.g., non-functioning can opener).

FIGS. 14B-14D show examples of this defect recording process. At step 1,the user opens or selects one or many defects. Here, the same defect canbe selected more than once (FIG. 14B). The user may then select thelocation, enter the number of non-conforming units and the number ofdefects per defect (FIG. 14C). As mentioned above, the user has theoption of adding pictures or notes for each defect recorded (FIG. 14D)by pressing either the notes 300 or picture 302 buttons.

FIGS. 14E and 14F show example displays for the pictures of defectslogged or to be added. The QM application management system of thepresent principles can be programmed to accommodate as many images asdesired. In the present example, 4 defect images can be taken and loadedinto the inspection record.

FIG. 15 shows an exemplary layout of a previous notifications screen(layer 9). Occasionally users will want to know what defects have beenlogged for the materials in their work list. As such, this data willneed to be pulled and available in the quality management application ofthe present invention. This previous defect information will berefreshed every time there is a new material added to the work list, andwill include all previous defects sorted by the factory. It iscontemplated herein that this layer will be accessible from a linkprovided on layer 1, the main menu of the QM application.

From the previous notifications screen (layer 9), a user can select anindividual defect. This will transition them to the notification detailscreen (layer 10) shown in FIG. 16, where they will see defect detailsincluding material number, description defect status, defect code, and adefect description or detail.

FIG. 17 shows an example of the Inspection procedures display screen.This is where the inspection procedures will be provided. This will be afull download when the QM application is initially provisioned. In thebackground, this will serve as the data store for inspection detailsfound in layer 7. When accessed via the main menu of layer 1, it willserve as a searchable database of material specific procedures.

FIG. 18 shows an example of the procedure detail screen (layer 12)according to an implementation. This is where specific inspectiondetails will be provided, beyond that provided in the general inspectionprocedures screen. Any and all specific inspection details may beprovided on this screen. The inspection procedure display screens oflayers 11 (FIG. 17) and 12 (FIG. 18) enable the QM management system toprovide inspection instructions to new or less experienced inspectors,and lessens the amount of time necessary to train such inspectors atthese procedures.

According to a further implementation, layer 13 of the QM Managementsystem is where inspection video demonstrations can be provided (FIG.19). All videos would be downloaded once the QM management applicationis provisioned and will allow the inspector to view inspection videosand requirements by material. The video details (e.g., the video file)would be provided in another layer 14 (FIG. 20).

FIG. 21 shows another layer (layer 15) where the Gold Sample would beprovided. For each material being inspection, there should be a goldsample on the system for comparison purposes. This gold sample can haveone or more pictures of the item being inspected and is configured to bethe only information what would occupy region D in the application.

These and other features and advantages of the present principles may bereadily ascertained by one of ordinary skill in the pertinent art basedon the teachings herein. It is to be understood that the teachings ofthe present principles may be implemented in various forms of hardware,software, firmware, special purpose processors, or combinations thereof.

Most preferably, the teachings of the present principles are implementedas a combination of hardware and software. Moreover, the software may beimplemented as an application program tangibly embodied on a programstorage unit. The application program may be uploaded to, and executedby, a machine comprising any suitable architecture. Preferably, themachine is implemented on a computer platform having hardware such asone or more central processing units (“CPU”), a random access memory(“RAM”), and input/output (“I/O”) interfaces. The computer platform mayalso include an operating system and microinstruction code. The variousprocesses and functions described herein may be either part of themicroinstruction code or part of the application program, or anycombination thereof, which may be executed by a CPU. In addition,various other peripheral units may be connected to the computer platformsuch as an additional data storage unit and a printing unit.

It is to be further understood that, because some of the constituentsystem components and methods depicted in the accompanying drawings arepreferably implemented in software, the actual connections between thesystem components or the process function blocks may differ dependingupon the manner in which the present principles are programmed. Giventhe teachings herein, one of ordinary skill in the pertinent art will beable to contemplate these and similar implementations or configurationsof the present principles.

Although the illustrative embodiments have been described herein withreference to the accompanying drawings, it is to be understood that thepresent principles is not limited to those precise embodiments, and thatvarious changes and modifications may be effected therein by one ofordinary skill in the pertinent art without departing from the scope orspirit of the present principles. All such changes and modifications areintended to be included within the scope of the present principles asset forth in the appended claims.

What is claimed is:
 1. A mobile Quality Management Inspection Systemcomprising: a mobile device in communication with at least one networkserver, the mobile device having a display screen and input means forinputting data, said data including photographs; and a database incommunication with the network server and configured to receive andstore all data input to the mobile device during an on site inspection,the network server configured to perform, according to the data inputthe mobile device, a usage decision process and a non-conformanceprocess, the usage decision process includes the network serverautomatically performing the steps of: determining whether a sample inthe inspection lot meets a gold seal acceptance standard; updating aquality information record if the sample meets the gold seal acceptablestandard; determining whether the source inspection is rejected withre-inspection; generating an indication to block the inbound delivery ofthe lot and creating a re-inspection of the lot when the sourceinspection is rejection with re-inspection; identifying a failure of theinspection lot when the source inspection is not rejected withre-inspection; and creating a new source inspection lot when there hasbeen an identified failure; wherein the mobile device is configured toenable an inspector to perform, on site, at least one of sourceinspection; receiving inspection; product qualification inspection;social compliance, Customs-Trade Partnership Against Terrorism (CTPAT)and factory valuations; non-conformance processing and documentmanagement, and upload this information to the database in real time. 2.The system according to claim 1, wherein the network server is furtherconfigured for: creating an inspection lot in response to a vendor'scompletion of an order; recording inspection results using a mobiledevice in communication with the at least one network server, the mobiledevice having a display screen and input means for inputting data, saiddata including photographs; performing the usage decision process onaccepted inspection lots, said accepted inspection lots having noidentified defects; and performing the non-conformance process onunaccepted inspections lots, said unaccepted inspection lots having atleast one defect.
 3. The system of claim 2, wherein said recordingfurther comprises: performing an on-site quality control productinspection of one or more lots of products at a factory manufacturingthe same; and recording such inspection results in real time.
 4. Thesystem of claim 2, wherein said performing a non-conformance processfurther comprises: selecting a quality notification from a list ofquality notifications; adding tasks associated with the selected qualitynotification; assigning users to each added task; receivingnotifications from the assigned users as to the completion of eachassigned task; recording a usage decision based on the completion oftasks, said recording closing the inspection lot; and determiningwhether to close quality notification relating to the inspection lot. 5.The system of claim 2, wherein the creation of the inspection lotfurther comprises: opening a window on a tablet to record characteristicresults, once recorded, the window is closed; determining whether anydefects are found in the inspection lot; recording defects any defectsfound in the inspection lot; for each product where no defects arefound, saving the inspection lot; calculating the number of recordeddefects in the inspection lot; comparing the calculated number ofrecorded defects with a predetermined value; sending an electroniccommunication to a vendor responsible for the inspection lot providingthe comparison results; determining whether or not to accept theinspection lot; creating a quality notification and assigning acoordinator when it is determined not to accept the inspection lot; andcompleting an acceptance of a usage decision process when it isdetermined to accept the inspection lot.